This repository was archived by the owner on Apr 6, 2021. It is now read-only.
Add autoprefixer known limitation to readme #53
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When I first tried to use the new compiler, I bumped into this error: `Maximum call stack size exceeded` Thanks to #29, I noticed that I must use the latest version of the `autoprefixer`, which indeed fixed this issue. Unfortunately, it can't be found anywhere in the docs.
|
Hey thanks for this! I don't think this is really a limitation of our library though, it's just a bug in another library. I'll merge this but rework it to include the note in a way that I think makes more sense though, thanks. |
|
Makes sense! Glad I could help :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I first tried to use the new compiler, I bumped into this error:
Maximum call stack size exceededThanks to #29, I noticed that I must use the latest version of the
autoprefixer, which indeed fixed this issue.Unfortunately, it can't be found anywhere in the docs.